Merged
Conversation
|
Is this way still able to prevent incompatible NumPy ABI versions? |
Member
Author
|
Yep. That is the goal ;-) |
isuruf
approved these changes
Aug 7, 2017
|
OK, I'll apply that to the other NumPy dependent packages I maintain then! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some changes to reflect the
numpy 1.8packages. Onlymatplolibandpandasare taking advantage ofnumpy 1.7and, b/c it would need to be patched to build on Python 3.5 and 3.6, I decided to just drop it from the docs. That does not mean people cannot use it if they want and they know what they are doing.@jjhelmus or @isuruf can you take a quick look at this?
Ping @pkg.